Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces enterprise-level constitution management capabilities to the spec-driven development workflow, enabling organizations to define and enforce organization-wide principles that govern all project-level constitutions.
Changes:
- Adds new
/speckit.enterprise-constitutioncommand to create and manage organization-wide governing principles - Updates project constitution workflow to require alignment with higher-level enterprise constitution
- Enhances spec and task templates to support external work item tracking (GitHub Issues, Azure DevOps)
- Improves task guidance to emphasize small, focused commits and external system integration
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| templates/commands/enterprise-constitution.md | New command template for creating/updating organization-wide constitution that all projects must obey |
| templates/commands/constitution.md | Updated to retrieve and align with enterprise constitution from canonical repository |
| templates/spec-template.md | Added sections for project context and external story/task tracking integration |
| templates/commands/specify.md | Enhanced to populate external story and task references in specifications |
| templates/commands/tasks.md | Updated to reference external task IDs and avoid duplicating workflow state from external systems |
| templates/tasks-template.md | Added guidance for small, focused tasks and one commit per task preference |
| spec-driven.md | Updated documentation to explain two-tier constitution hierarchy |
| docs/quickstart.md | Added enterprise constitution setup step with examples |
| README.md | Added enterprise-constitution command to command reference table |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+58
to
+65
| - Delivery Discipline & Change Management (for example, small, | ||
| incremental, independently reviewable changes) | ||
| - For governance, define at least: | ||
| - Who can propose amendments. | ||
| - How changes are reviewed and approved. | ||
| - How often the constitution should be revisited. | ||
| - How conflicts with project-level constitutions are resolved. | ||
| - How work is expected to be sliced and delivered (for example, |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Lines 58 and 65 have 7 spaces of indentation while the surrounding bullets have 6 spaces. This breaks the visual hierarchy and may affect Markdown rendering.
Suggested change
| - Delivery Discipline & Change Management (for example, small, | |
| incremental, independently reviewable changes) | |
| - For governance, define at least: | |
| - Who can propose amendments. | |
| - How changes are reviewed and approved. | |
| - How often the constitution should be revisited. | |
| - How conflicts with project-level constitutions are resolved. | |
| - How work is expected to be sliced and delivered (for example, | |
| - Delivery Discipline & Change Management (for example, small, | |
| incremental, independently reviewable changes) | |
| - For governance, define at least: | |
| - Who can propose amendments. | |
| - How changes are reviewed and approved. | |
| - How often the constitution should be revisited. | |
| - How conflicts with project-level constitutions are resolved. | |
| - How work is expected to be sliced and delivered (for example, |
Comment on lines
+58
to
+67
| - Delivery Discipline & Change Management (for example, small, | ||
| incremental, independently reviewable changes) | ||
| - For governance, define at least: | ||
| - Who can propose amendments. | ||
| - How changes are reviewed and approved. | ||
| - How often the constitution should be revisited. | ||
| - How conflicts with project-level constitutions are resolved. | ||
| - How work is expected to be sliced and delivered (for example, | ||
| small, focused tasks; narrow pull requests; and incremental, | ||
| revertible changes tied to clear Task and story IDs). |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Lines 65-67 have 7 spaces of indentation while the surrounding bullets have 6 spaces. This breaks the visual hierarchy and may affect Markdown rendering.
Suggested change
| - Delivery Discipline & Change Management (for example, small, | |
| incremental, independently reviewable changes) | |
| - For governance, define at least: | |
| - Who can propose amendments. | |
| - How changes are reviewed and approved. | |
| - How often the constitution should be revisited. | |
| - How conflicts with project-level constitutions are resolved. | |
| - How work is expected to be sliced and delivered (for example, | |
| small, focused tasks; narrow pull requests; and incremental, | |
| revertible changes tied to clear Task and story IDs). | |
| - Delivery Discipline & Change Management (for example, small, | |
| incremental, independently reviewable changes) | |
| - For governance, define at least: | |
| - Who can propose amendments. | |
| - How changes are reviewed and approved. | |
| - How often the constitution should be revisited. | |
| - How conflicts with project-level constitutions are resolved. | |
| - How work is expected to be sliced and delivered (for example, | |
| small, focused tasks; narrow pull requests; and incremental, | |
| revertible changes tied to clear Task and story IDs). |
| - Version change: old → new. | ||
| - List of added, modified, and removed principles. | ||
| - Governance changes. | ||
| - Where the canonical file is stored (repository + path, and commit/ref if known). |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Line 104 has 7 spaces of indentation while the surrounding bullets have 6 spaces. This breaks the visual hierarchy and may affect Markdown rendering.
Suggested change
| - Where the canonical file is stored (repository + path, and commit/ref if known). | |
| - Where the canonical file is stored (repository + path, and commit/ref if known). |
| - If contracts/ exists: Map endpoints to user stories | ||
| - If research.md exists: Extract decisions for setup tasks | ||
| - Generate tasks organized by user story (see Task Generation Rules below) | ||
| - Generate tasks organized by user story (see Task Generation Rules below) |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Line 43 has 5 spaces of indentation while other sub-bullets in the same section have 6 spaces. This breaks the visual hierarchy and may affect Markdown rendering.
Suggested change
| - Generate tasks organized by user story (see Task Generation Rules below) | |
| - Generate tasks organized by user story (see Task Generation Rules below) |
| - Read `/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). | ||
| - Read each command file in `/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. | ||
| - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. | ||
| - If `/memory/enterprise-constitution.md` exists and has been updated outside this command, ensure that any project-level references to enterprise principles still point to valid sections or concepts. |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Line 64 has 5 spaces of indentation while other sub-bullets in step 5 have 6 spaces. This breaks the visual hierarchy and may affect Markdown rendering.
Suggested change
| - If `/memory/enterprise-constitution.md` exists and has been updated outside this command, ensure that any project-level references to enterprise principles still point to valid sections or concepts. | |
| - If `/memory/enterprise-constitution.md` exists and has been updated outside this command, ensure that any project-level references to enterprise principles still point to valid sections or concepts. |
| - Removed sections | ||
| - Templates requiring updates (✅ updated / ⚠ pending) with file paths | ||
| - Enterprise alignment summary: | ||
| - Whether the enterprise constitution was successfully retrieved from its canonical repository and whether `/memory/enterprise-constitution.md` was present/updated as a cache. |
There was a problem hiding this comment.
Inconsistent indentation in the bullet list. Line 73 has 8 spaces of indentation while the sibling bullet on line 74 has 6 spaces. This creates visual inconsistency and may affect Markdown rendering.
Suggested change
| - Whether the enterprise constitution was successfully retrieved from its canonical repository and whether `/memory/enterprise-constitution.md` was present/updated as a cache. | |
| - Whether the enterprise constitution was successfully retrieved from its canonical repository and whether `/memory/enterprise-constitution.md` was present/updated as a cache. |
| @@ -1,5 +1,4 @@ | |||
| --- | |||
| description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync. | |||
| description: Create or update the project constitution from interactive or provided principle inputs, ensuring it aligns with the higher-level enterprise constitution and all dependent templates stay in sync. | |||
There was a problem hiding this comment.
The YAML frontmatter is missing its opening delimiter. Markdown files with YAML frontmatter require both opening and closing --- delimiters. The opening --- should precede the description: field.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.